Providing sketch annotations with multimedia programs

ABSTRACT

A method for collaborative sketch annotating of a program of multimedia content includes enabling a first user to create a sketch annotation, enabling the first user to store sketch annotation data related to the sketch annotation, and enabling a second user to access the sketch annotation. The second user may navigate the program using the sketch annotation and/or an indication of the sketch annotation. The first user may create the sketch annotation while viewing the program, for example, and the program may be paused for adding the sketch annotation to one or more paused frames. The sketch annotations may include chronological information indicative of a chronological location of the sketch annotation within the program.

BACKGROUND

1. Field of the Disclosure

The present disclosure relates to multimedia services, and moreparticularly, to providing sketch annotations related to multimediacontent in a social networking environment.

2. Description of the Related Art

Social networking related to multimedia programs is often conductedthrough means that are separate from a provider network that providesthe multimedia content. For example, friends that want to discussmultimedia programs often do so over telephones, through in-personinteractions, or through text-based communications (e.g., email and textmessaging). Discussions of multimedia programs are often limited toverbal communications (i.e., communications that use only words).

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of selected elements of a multimedia contentdistribution network;

FIG. 2 is a block diagram of selected elements of an embodiment of amultimedia processing resource suitable for supporting a collaborativesketch annotation application;

FIG. 3 is a block diagram of selected elements of an embodiment of aserver suitable for hosting a collaborative sketch annotationapplication;

FIG. 4 depicts a display with an embodiment of a graphical userinterface for supporting collaborative sketch annotations;

FIG. 5 depicts an embodiment of a mobile communication device foraccepting user inputs to create sketch annotations;

FIG. 6 is a flow diagram of selected elements of a service that enablescollaborative sketch annotating of multimedia content;

FIG. 7 is a flow diagram of selected elements of an embodiment of amethod that supports collaborative sketch annotations for a program ofmultimedia content; and

FIG. 8 is a flow diagram of selected elements of another embodiment of asketch annotation method.

DESCRIPTION OF THE EMBODIMENT(S)

In one aspect, a disclosed service allows for collaborative sketchannotating of multimedia content. A first user is enabled to createsketch annotations for a multimedia program using a first client such asa set-top box (STB) or other customer premises equipment (CPE). Thesketch annotation may be hand-drawn and may be coded to distinguish itfrom sketch annotations of other users. Accordingly, sketch annotationsmay be received from a touch screen entered manually or with a stylus.In some embodiments, a personal digital assistant (PDA), mobilecommunication device (e.g., cellular telephone), or remote controldevice equipped with motion sensing equipment may be enabled to detectmovement and thereby accept user input for creating sketch annotations.Data indicative of the sketch annotation is stored and a second user ofa second client is enabled to view the sketch annotation while viewingthe program. The sketch annotation may be associated with chronologicalinformation that indicates the chronological location of the sketchannotation within the program. The second user of the second client mayview the sketch annotations asynchronously compared to viewings by otherusers and compared to when they are made. The sketch annotations may beviewed at any time after they are made in some embodiments.

In another aspect, a disclosed data processing system that is suitablefor use in a multimedia content delivery network includes a processorthat has access to tangible, computer readable storage, which may beconcentrated in a single storage entity or distributed among a pluralityof storage entities. The storage includes embedded and executableinstructions (i.e., software) for collaborative sketch annotation of amultimedia content program. Disclosed software has instructions forgenerating a sketch annotation in response to a first user providing asketch annotation request, storing data indicative of the sketchannotation, recognizing a second user as a member of a collaborationgroup, and providing the sketch annotation to the second user. Thesketch annotation may be generated while the first user is viewing theprogram, and the first user may provide input to pause the program whilethe sketch annotation is created. The sketch annotation may beassociated with or include chronological information indicative of itslocation (i.e., temporal location) within the program. A graphicalelement such as a timeline may be presented to users of a collaborationgroup and may include indications (e.g., sketch annotation icons) ofwhere sketch annotations from multiple users appear throughout aprogram. Each indication of a sketch annotation and each sketchannotation may be coded to allow users to determine which user createdit. For example, each sketch annotation and/or indication of sketchannotation may be color-coded or labeled to attribute it to its author.Sketch annotations may be created while one or more users are viewing aprogram, and further, different users may be viewing different portionsof the program at a given time. Sketch annotations and indications ofsketch annotations, in some embodiments, are dynamically updated foreach user within a collaboration group regardless of which portion ofthe program is being viewed by members of the collaboration group at agiven time. Input used to create sketch annotations may come fromhardware devices including but not limited to remote control deviceswith motion detection equipment (e.g., accelerometers), touch screeninterfaces on mobile devices, and displays with sensors for receivingon-screen input (e.g., laser input) from remote control devices.

In still another aspect, a disclosed method supports users within asketch annotation group providing and viewing collaborative sketchannotations associated with a multimedia program. The method includes afirst user of a sketch annotation group initiating entry of acontemporaneously generated, free-form, sketch annotation. Sketchannotation data indicative of the sketch annotation is stored and thesketch annotation data is associated with a selected chronologicallocation within the program. If a second user of the sketch annotationgroup requests the program, the second user is provided access to thesketch annotation in conjunction with the program. The second user mayuse sketch annotation data to navigate the multimedia content based onthe sketch annotation and view information indicative of the sketchannotation while viewing the selected chronological location. The sketchannotation may be superimposed on one or more images of the program thatwere displayed to the user when the user provided the sketchannotations. Each sketch annotation may be coded (e.g., color-coded) toattribute it to its author.

In still another aspect, a disclosed collaboration sketch annotationmethod includes enabling a plurality of users to provide sketchannotations that are associated with a program of multimedia content,storing sketch annotation data indicative of the sketch annotations, andenabling one or more of the plurality of users to access the storedsketch annotation data and display the sketch annotations while theprogram is playing. A first user may define the plurality of users(e.g., a collaboration group) that are provided access to the storedsketch annotation data. The plurality of users may navigate the programusing indications of the sketch annotations. For example, a user mayselect an indication of a sketch annotation (e.g., a sketch annotationicon presented on a graphical timeline) made during the beginning of theprogram and consequently may be presented with corresponding portions ofthe beginning of the program.

The sketch annotation may include an image indicative of the content orframe that was displayed when the user asserted the annotation button orotherwise created the sketch annotation. The sketch annotation mightinclude information indicative of the sketch annotation's author andother annotation content including text, an audio segment, an image, ora video segment selected by the viewer or other author of the sketchannotation. The sketch annotations may be chronologically ordered andmight include chronological information indicative of a chronologicallocation of the sketch annotation within the program.

In the following description, details are set forth by way of example tofacilitate discussion of the disclosed subject matter. It should beapparent to a person of ordinary skill in the field, however, that thedisclosed embodiments are exemplary and not exhaustive of all possibleembodiments. Throughout this disclosure, a hyphenated form of areference numeral refers to a specific instance of an element and theun-hyphenated form of the reference numeral refers to the elementgenerically or collectively. Thus, for example, widget 12-1 refers to aninstance of a widget class, which may be referred to collectively aswidgets 12 and any one of which may be referred to generically as awidget 12.

Turning now to the drawings, FIG. 1 is a block diagram illustratingselected elements of an embodiment of a multimedia content deliverynetwork (MCDN 100). The depicted embodiment of MCDN 100 includesfunctionality to facilitate collaborative sketch annotating of amultimedia content stream and possibly enhanced navigation of sketchannotated streams based on the sketch annotations themselves. Althoughmultimedia content is not limited to television, video-on-demand, orpay-per-view programs, the depicted embodiments of MCDN 100 and itscapabilities are described herein with primary reference to these typesof multimedia content, which are interchangeably referred to herein asmultimedia content program(s), multimedia programs or, simply, programs.

The elements of MCDN 100 illustrated in FIG. 1 emphasize the network'sfunctionality for delivering multimedia content to one or more users(e.g., subscribers). As depicted in FIG. 1, MCDN 100 includes one ormore clients 120, where each client may represent a different usersubscriber, and a service provider 121 that encompasses resources toacquire, process, and deliver programs to clients 120. Clients 120 andservice provider 121 are demarcated by an access network 130 to whichclients 120 and service provider 121 are connected. In some embodiments,access network 130 is an Internet protocol (IP) network, while in otherembodiments, access network 130 may be implemented as a conventionalcoaxial-based network. In IP implementations of access network 130,access network 130 may employ a physical layer of unshielded twistedpair cables, fiber optic cables, or both. As an example, MCDN 100 mayemploy digital subscriber line (DSL) compliant twisted pair connectionsbetween clients 120 and a node (not depicted) in access network 130while fiber cable or other broadband cable connects service providerresources to a node in access network 130. In other embodiments, thebroadband cable may extend all the way to clients 120.

The clients 120 depicted in FIG. 1 include a network applianceidentified as CPE 122 that connects to access network 130 and to amultimedia processing resource (MPR) 124. CPE 122 may supply routing,firewall, or other services for clients 120. CPE 122 may includeelements of a broadband modem such as an asynchronous DSL (ADSL) modemas well as elements of a local area network (LAN) access point thatsupports a LAN 123 to which MPR 124 connects. LAN 123 may, in someembodiments, represent an Ethernet compliant LAN, also sometimesreferred to as an IEEE 802.11 LAN. Clients 120 as depicted in FIG. 1further include a display device or, more simply, a display 126. Aremote control device 128 of client 120 is operable to communicatewirelessly to MPR 124 using infrared (IR) or radio frequency signals asis well known. MPRs 124 may receive input via buttons (not depicted)located on side panels of MPRs 124. MPR 124 may be implemented as astand-alone STB suitable for use in a co-axial or IP-based multimediacontent delivery network. In other embodiments, MPR 124 may beintegrated with display 126, CPE 122, or both.

Referring to FIG. 2, a block diagram illustrating selected elements ofMPR 124 is presented. In the depicted embodiment, MPR 124 includes aprocessor 201 coupled to storage media collectively identified asstorage 210 via a shared bus 202. Storage 210 encompasses persistent andvolatile media, fixed and removable media, and magnetic andsemiconductor media. Storage 210 is operable to store instructions,data, or both. Storage 210 as shown includes multiple sets or sequencesof instructions, namely, an operating system 212, sketch annotation data216, an application program identified as sketch annotation andcollaboration support 214, and an application program identified asenhanced navigation application 218.

Operating system 212 may be a Unix® or Unix-like operating system, aWindows® family operating system, or another suitable operating system.Sketch annotation and collaboration support 214, as suggested by itsname, may operate in conjunction with a sketch annotation application,which may be hosted on an application server or content delivery serverof service provider 121, to facilitate collaborative sketch annotationof a program of multimedia content. Enhanced navigation application 218may include instructions to implement sketch-annotation-based navigationof sketch annotated programs and may further include instructions tosupport criteria based identification of desired locations within asketch annotated program. IR receiver 337 receives input from a remotecontrol device (e.g., remote control device 128-1 from FIG. 1). In someembodiments, IR receiver 337 receives input from a remote control devicewith a touch screen that accepts input regarding the location, shape,and scale of a sketch annotation. The remote control device may be asmart phone, a laptop computer, or other electronic device. Although theembodiment of IR receiver 337 in FIG. 2 uses infrared signals, radiofrequency communication and other protocols and technologies may be usedto receive user input indicative of the shape, scale and location of asketch annotation as specified by a sketch annotation author. A remotecontrol device in communication with IR receiver 337, in someembodiments, detects motion of a user's hand indicative of the shapethat the user wants for the sketch annotation. Remote controlapplication 288, as shown in FIG. 2, processes user input received by IRreceiver 337 and generates sketch annotation data used to form anddisplay sketch annotations processed by MPR 124 and possibly othermultimedia processing resources (e.g., other STBs).

The implementation of MPR 124 depicted in FIG. 2 includes a datastructure identified as sketch annotation data 216 and a data structureidentified as local copy 219, which represents a copy of the program ofmultimedia content. Sketch annotation data 216 includes data thatrepresents or is otherwise indicative of sketch annotations createdusing the collaborative sketch annotation application 330 (FIG. 3) andsketch annotation and collaboration support 214 described herein. Inthis embodiment, sketch annotation data 216 is maintained as a datastructure that is separate and distinct from the program to which thesketch annotation data corresponds. In this implementation, sketchannotation data 216 may be freely exchanged among users within a definedgroup independent of the underlying program. Each user may then downloador otherwise acquire a resident copy of a program, an example of whichis illustrated in FIG. 2 as local copy 219. Thereafter, the sketchannotation may be transferred or accessed as needed to reflect additionsor other modifications to the sketch annotation data 216.

MPR 124, as depicted in FIG. 2, further includes a network adapter 220that interfaces MPR 124 to LAN 123. In some embodiments, MPR 124receives multimedia content through LAN 123. In embodiments suitable foruse in IP based content delivery networks, MPR 124, as depicted in FIG.2, may include a transport unit 230 that assembles the payloads from asequence or set of network packets into a stream of multimedia contentthat includes sketch annotations. In coaxial based access networks,content may be delivered as a stream that is not packet based and it maynot be necessary in these embodiments to include transport unit 230. Ina co-axial implementation, however, clients 120 may require tuningresources (not explicitly depicted in FIG. 1) to “parse” desired contentfrom other content that is delivered over the coaxial mediumsimultaneously and these tuners may be provided in MPRs 124. The streamof multimedia content received by transport unit 230 may include audioinformation and video information and transport unit 230 may parse orsegregate the two to generate a video stream 232 and an audio stream 234as shown.

Video and audio streams 232 and 234, as output from transport unit 230,may include audio or video information that is compressed, encrypted, orboth. A decoder unit 240 is shown as receiving video and audio streams232 and 234 and generating native format video and audio streams 242 and244. Decoder 240 may employ any of various widely distributed videodecoding algorithms including any of the Motion Pictures Expert Group(MPEG) standards, Windows Media Video (WMV) standards including WMV 9,which has been standardized as Video Codec-1 (VC-1) by the Society ofMotion Picture and Television Engineers. Similarly decoder 240 mayemploy any of various audio decoding algorithms including Dolby®Digital, Digital Theatre System (DTS) Coherent Acoustics, and WindowsMedia Audio (WMA).

The native format video and audio streams 242 and 244 as shown in FIG. 2may be processed by encoders/digital-to-analog converters(encoders/DACs) 250 and 260 respectively to produce analog video andaudio signals 252 and 262 in a format compliant with display 126, whichitself may not be a part of MPR 124. Display 126 may comply with aNational Television Systems Committee (NTSC), Phase Alternating Line(PAL) or any other suitable television standard.

Returning now to FIG. 1, the selected elements representing serviceprovider 121 include content acquisition resources 180 connected to aswitch 140 via a backbone network 170. An application server 150 and acontent delivery server 160 are also shown connected to switch 140.Switch 140 may provide firewall and routing functions to demarcateaccess network 130 from the resources of service provider 121. Switch140 may be housed in a central office or other facility of serviceprovider 121. In embodiments that employ DSL compliant connections,switch 140 may include elements of a DSL Access Multiplexer (DSLAM) thatmultiplexes many subscriber DSLs to backbone network 170. Backbonenetwork 170 represents a private network including, as an example, afiber based network to accommodate high data transfer rates. Contentacquisition resources 180 as depicted in FIG. 1 encompass theacquisition of various types of content including broadcast content,other “live” content including national content feeds, andvideo-on-demand content.

Acquired content is provided to a content delivery server 160 viabackbone network 170 and switch 140. Content may be delivered fromcontent delivery server 160 to clients 120 via switch 140 and accessnetwork 130. Content may be compressed, encrypted, modulated,demodulated, and otherwise encoded or processed at content acquisitionresources 180, content delivery server 160, or both. Although FIG. 1depicts a single element encompassing acquisition of all content,different types of content may be acquired via different types ofacquisition resources. Similarly, although FIG. 1 depicts a singlecontent delivery server 160, different types of content may be deliveredby different servers. Moreover, embodiments of MCDN network 100 mayinclude content acquisition resources in regional offices that areconnected to switch 140.

Although the service provider 121 is depicted in FIG. 1 as having asingle switch 140 to which content acquisition resources 180, contentdelivery server 160, and application server 150 are connected, otherembodiments may employ different switches for each of these functionalcomponents and may include additional functional components not depictedin FIG. 1 including, for example, operational subsystem support (OSS)resources.

FIG. 1 illustrates application server 150 connected to switch 140. Assuggested by its name, application server 150 may host or otherwiseimplement one or more applications for MCDN 100. Applications providedby application server 150 may be downloaded and hosted on other networkresources including, for example, content delivery server 160, switch140, CPE 122, and/or MPR 124.

Referring to FIG. 3, a block diagram depicts selected elements of anembodiment of application server 150 including support for collaborativesketch annotation as described herein. In the depicted embodiment,application server 150 includes at least one processor 301 that isoperable to access storage 310 via a shared bus 302. A network interfacecard (NIC) 320 connects to the shared bus 302 and supports communicationbetween processor 310 and network connected resources.

In the depicted embodiment, storage 310 of application server 150includes instructions that define an operating system 325, acollaborative sketch annotation application 330, and an enhancednavigation application 340. As depicted in FIG. 3, application server150 has networked access to remote data structures including anannotation data structure 350 and a collaboration group data structure360 that may be used in conjunction with collaborative sketch annotationapplication 330. In other embodiments, the data represented by datastructures 350 and/or 360 may be included within storage 310.Collaborative sketch annotation application 330 is enabled to processuser input data generated from a sketch annotation author that specifiesthe shape, size, and location of the sketch annotation relative toelements in a frame or frames of a multimedia program.

Enabling the first user to create the sketch annotation may includeenabling the first user to create the sketch annotation “on-the-fly,”i.e., while the first user is viewing the program. Creating a sketchannotation may, for example, be achieved by asserting an annotationbutton on a remote control device. The sketch annotation may then becreated by the user providing user input (e.g., motion input) to aremote control device. If the remote control device containsaccelerometers for example, embodied remote control devices may processdata from the accelerometers to detect the shape, location, and size ofan author's desired sketch annotation. A multimedia processing resource(e.g., an STB) may then receive data detected by the remote controldevice and process it to locate, scale and overlay the sketch annotationonto one or more frames of a program of multimedia content. User inputthat determines the shape, location, and size of sketch annotations maybe received over a multitude of devices including mobile communicationdevices with touch screens, remote control devices that detect motionthrough accelerometers, input from a mouse, input from a laser pointer,and the like.

The sketch annotation may include sketch annotation content andchronological information. The sketch annotation content may include animage indicative of the content displayed when the user asserted thesketch annotation button. For example, the sketch annotation content mayinclude a “screen shot” or an image of the frame that was beingdisplayed when the user asserted the sketch annotation button. Thesketch annotation content, in addition to other free-form content, mayalso include hand-drawn text, an audio segment, a different image, and avideo segment selected by the viewer or author of the sketch annotation.The chronological information of a sketch annotation may includeinformation indicative of a chronological location within the program ofthe sketch annotation. In some embodiments, the sketch annotations arechronologically ordered on a timeline overlayed on the program orotherwise displayed with the program.

Disclosed embodiments enable users to store data indicative of thesketch annotation. The user may be enabled to store the sketchannotation as a data structure that is apart and distinct from themultimedia content to which the sketch annotation data pertains. Theuser may be enabled to store the sketch annotation locally, e.g., instorage 210 of MPR 124 or in a networked storage resource including, asan example, storage 310 of application server 150.

Sketch annotation authors may create sketch annotations for viewing by acollaboration group that includes the author (e.g., a collaborationgroup member) and further users (e.g., other collaboration groupmembers). When any collaboration group member requests the program forviewing, a sketch annotation application (e.g., collaborative sketchannotation application 330 from FIG. 3) may inform the user that he orshe has been included in the sketch annotation author's collaborationgroup. The application may then prompt the user to determine if he orshe consents to inclusion in the collaboration group. If the userconsents to inclusion in the collaboration group, the application (e.g.,collaborative sketch annotation application 330 from FIG. 3) may thenmake the sketch annotation data accessible to the user.

An embodied collaborative sketch annotation service may support enhanceduser-navigation of a program by advancing a user to a chronologicallocation within the program that satisfies certain sketch annotationcriteria. For example, a user may be interested in finding or otherwisenavigating to a location within the program where his girlfriend leftsketch annotations. Alternatively, the user may seek a portion of theprogram with a high density of sketch annotations. To find any suchlocations, the user may specify a sketch annotation density criteria ofN sketch annotations/minute. In this case, a sketch annotationapplication (e.g., collaborative sketch annotation application 330 inFIG. 3) may search sketch annotation data and determine, fromchronological information associated with each sketch annotation or byother techniques, one or more locations in the program where there are Nor more sketch annotations within a 60 second window. In someembodiments, the collaborative sketch annotation application thendisplays the program, if the program is not already being displayed, andadvances the program to one of the locations identified as satisfyingthe specified criteria. In some instances, the application may advancethe user to the first encountered location satisfying the criteriawhile, in other instances, the application may advance the user to thelocation that has the greatest sketch annotation density or to anotherlocation that satisfies the criteria.

FIG. 4 depicts an exemplary display 401 for displaying a program ofmultimedia content and sketch annotations in accordance with disclosedembodiments. Avatars 403 correspond to members of collaboration group413. Member 403-1 “wears” a number 11 for identification purposes forthe benefit of other group members. Similarly, member 403-2 wears anumber 53 and group member 403-3 wears a number 66. Sketch annotation472 encircles a tire of the left-most car on the display. In someembodiments, the sketch annotation 472 may automatically “follow” thecar and remain encircling the tire during motion of the display. Asshown, sketch annotation 472 includes an indicator (i.e., text “53”)that identifies the sketch annotation as having been created by groupmember 403-2. Display 401 also includes sketch annotation 415, which asshown, is a hand-drawn “X” and curved arrow that may becontemporaneously generated in a free form manner while a user isviewing the program. Sketch annotation 415 also includes an identifier(i.e., text “53”) that indicates group member 403-2 is the author of thesketch annotation. In some embodiments, the image shown on display 401is automatically paused upon the sketch annotation author requesting toadd a sketch annotation. Sketch annotation 415 may be configured by theauthor (i.e., group member 403-2) to show for a predetermined time ondisplay 401 or other user display or may automatically disappear upon asignification change (e.g., a scene change) of the program.

As shown in FIG. 4, display 401 presents timeline 409 that provides auser with chronological information for the program and also providesindications of sketch annotations. For example, indication (of sketchannotation) 405 is shown on the left part of timeline 409. Thispositioning of indication 405 suggests that the corresponding sketchannotation is associated with a frame or frames from the beginning ofthe program. In addition, the text “53” is part of indication 405 toinform a viewer that the author of the sketch annotation is group member403-2, which is associated with the number “53” as indicated by the texton the avatar associated with member 403-2. Similarly, indication (ofsketch annotation) 411 is associated with member 403-1 due to it showingthe number “11” and indication 407 is associated with member 403-3 dueto it showing the number “66.” The shaded portion 411 of timeline 409indicates a portion of the program that is occupied by commercials. Insome embodiments, sketch annotations are added to commercials. Timestamp425 informs a viewer that the frame shown on display 401 occurs onehour, fifty-two minutes, and thirty-six seconds into the program. Suchinformation, although not depicted, may be included with indications ofsketch annotations shown on a timeline (e.g., timeline 409).

FIG. 5 depicts a sketch annotation author's hand 507 manipulating astylus 505 on a touch screen on mobile communication device 501. Mobilecommunication device 501 may be a smart phone (e.g., an Iphone), a PDA,a remote control device, or similar device for receiving user input tocreate sketch annotations. The display on communication device 501includes the same frames as the program shown on display 401 (FIG. 4).The frames may be transmitted locally or through a cellular network, forexample, to the mobile communication device in response to a userrequesting to create a sketch annotation. Alternatively, the program maystream continuously to the mobile communication device 501 substantiallysimultaneously with it streaming to display 401. As shown, the stylus505 is used to create sketch annotation 515 that then appears as sketchannotation 415 on display 401 (FIG. 4) contemporaneously with itscreation or upon approval of its author to transmit it for sending todisplay 401 or a CPE communicatively coupled to display 401. As shown inFIG. 5, group 513 corresponds to collaboration group 413 (FIG. 4),avatar 503-1 corresponds to member 403-1, avatar 503-2 corresponds tomember 403-2, sketch annotation 515 corresponds to sketch annotation415, avatar 503-3 corresponds to member 403-3, sketch annotation 572corresponds to sketch annotation 472, and so on.

FIG. 6 depicts selected elements of a collaborative annotation service600. Service 600 may be performed, at least in part, by collaborativesketch annotation application 330. Using service 600, one or more usersare enabled to provide sketch annotations to multimedia programs topromote social networking. A first user is enabled (block 601) to createa sketch annotation for a program of multimedia content using a firstclient. The first user may be enabled to create the sketch annotation inresponse to a sketch annotation request. In conjunction, the first usermay be provided an opportunity to define a collaboration group bytransmitting a collaboration group request that includes informationthat identifies or otherwise indicates one or more other users toinclude with the collaboration group. Collaboration group members mightbe identified or indicated by, for example, their names, emailaddresses, street addresses, phone numbers, user identifications,personal identification numbers, pseudonyms, aliases, user names, and soforth. Sketch annotations associated with a particular program may beincorporated into a single sketch annotation data structure thatrepresents all sketch annotations (and possibly non-sketch annotations)created by any of the users in the collaboration group. In theseembodiments, any of the group members may then access the sketchannotation data and interact with it. In other embodiments, the sketchannotation data may include two or more sketch annotation datastructures. For example, the sketch annotation data may include separatedata structures for each group member. Whether sketch annotation data iscontained in a signal data structure or not, a user who accesses thesketch annotation data may have the ability to identify the users whosesketch annotations are of interest.

The sketch annotation may be a hand-drawn sketch annotation created withthe aid of a smart phone, a touch screen and stylus, a remote controldevice emitting an IR or laser signal that is detected, a remote controldevice enabled with accelerometers or other motion detecting equipment,and the like. Data indicative of the sketch annotation is stored (block603). The data indicative of the sketch annotation may be stored on astorage resource that is local to the first user or stored on anetworked resource that is or may be accessible to multiple users. Inaddition, chronological information indicative of a chronologicallocation of the sketch annotation within the program is stored (block605). A second user is enabled (block 607) to view the sketch annotationwhile viewing the program using a second client. The second user isenabled to navigate (block 611) to a segment of the program containingthe sketch annotation by selecting an indication of the sketchannotation. In some cases, indications of sketch annotations appear on agraphical timeline presented on a graphical display. The location of thesketch annotations on the graphical timeline indicate where, time-wise,the sketch annotations appear in a multimedia program. Embodied systems,methods, and services may enable users to navigate to a segment of theprogram containing the sketch annotation by selecting the indication ofthe annotation. In the embodied collaborative annotation service 600,the sketch annotation is removed (block 613) from displaying after aspecified duration, in response to a change in scene in the program, orif the sketch annotation no longer aligns to a displayed program image.

FIG. 7 illustrates collaborative sketch annotation method 700 forpromoting social networking by allowing users to share sketchannotations that are attached to, associated with, or presented as anoverlay upon multimedia programs. Collaborative annotation method 700may be performed or practiced by collaborative sketch annotationapplication 330 (FIG. 3), another application hosted by applicationserver 150 or another networked resource (not depicted) of MCDN 100. Thedepicted embodiment of collaborative annotation method 700 includesreceiving (block 701) a sketch annotation from a first user for overlayupon one or more frames of a multimedia program. The embodiment furtherincludes storing (block 703) annotation data for the sketch annotation.A second user provides a request that is received (block 705) to viewthe multimedia program. The sketch annotation is coded (block 706) todistinguish it from sketch annotations of other users. The second useris provided access (block 707) to the sketch annotation in conjunctionwith the second user receiving the multimedia program. The second useris presented (block 709) with visually detectable information indicativeof the sketch annotation. In some embodiments, the second user ispresented with an indication of the chronological location of the sketchannotation within the multimedia program. The second user is permitted(block 711) to navigate the multimedia content based on the sketchannotation. For example, by selecting the indication of the sketchannotation that is presented on a graphical timeline toward the end ofthe timeline, the user may navigate to the sketch annotation and towardthe end of the program. Specifically, the user would be directed towardthe frame or frames upon which the sketch annotation was made. A sketchannotation author may be enabled to specify sketch annotation criteria(e.g., define the makeup, location, and bounds of the sketch annotation)using a remote control and a graphical interface presented on a displayscreen.

FIG. 8 illustrates a method or service that promotes social networkingby allowing users to share sketch annotations with others that viewmultimedia programs. The depicted embodiment of collaborative sketchannotation method 800 includes enabling (block 801) a plurality of usersto sketch annotations to be associated with a multimedia program. Thesketch annotations are associated (block 803) with one or morechronological positions of the multimedia program. Sketch annotationdata indicative of the sketch annotations is stored (block 805) and atleast one user is enabled (block 807) to access the stored sketchannotation data. Sketch annotations are displayed (block 809) while themultimedia program is playing. Sketch annotations are coded (block 811)by author so that users can determine the source of a sketch annotation.

Embodied systems, methods, and services may enable a first user tocreate a sketch annotation while a second user is viewing the program.In such cases, a graphical interface presented to the second user may bedynamically updated to include timely indications of sketch annotationsprovided by other users in a collaboration group, for example. A sketchannotation author may initiate a sketch annotation mode by asserting(e.g., depressing) a sketch annotation button on a remote control devicewhile the author is viewing the program. In response, disclosed systemsmay pause the display of the multimedia program for the author and allowthe author to navigate to previous or future frames to choose frames onwhich to add sketch annotations. In some embodiments, the author ispresented an option for setting a predetermined duration for presentingthe sketch annotation to other users. Accordingly, sketch annotationsare removed from displaying after the specified duration. Embodiedsystems may associate each sketch annotation with distinct features(e.g., colors, avatars, icons, textual identifiers) to allow users todetermine the source of the sketch annotation.

There are many options for permitting sketch annotation authors toprovide data used to create sketch annotations and sketch annotationdata. For example, an author may create a sketch annotation by providinguser input to a mobile communication device communicatively coupled to afirst client (e.g. an STB). The mobile communication device (e.g., acellular telephone) may be communicatively coupled over a wirelesstelephone network, a local WiFi connection, a Bluetooth connection, awired connection, an infrared connection, a radio frequency connection,and the like. The mobile communication device may receive user inputusing a touch screen (with or without a stylus). Accordingly, creatingsketch annotations may include a user creating a trace of a movementwith a hardware element in the user's hand. For example, a user may wavehis or her hand in a tight circle to create a small sketched circle onthe display of the multimedia program. Accelerometers or other motionsensors within the remote control device may be used to effectively drawsketch annotations on a display. In some embodiments, a video camera maybe set up to communicate with a first client device (e.g., an STB) toestimate user movements intended to create sketch annotations. If thefirst client is configured to detect hand movement from a video camera,the first client and associated processors may be aided by a sketchauthor wearing a special colored glove or finger sleeve (i.e., a glovethat covers one finger) that is more easily detected by the videocamera.

In some embodiments, sketch annotations are aligned to elements of acurrent image of the program. For example, if a first user is watching afootball game and would like to emphasize or point out his or herfavorite player to a second user, the first user may sketch a circlearound the favorite player. Some embodied systems may automaticallytrack the favorite player as the favorite player moves about the displayduring football action. In some embodiments, the sketch annotation maybe removed from display if the sketch annotation no longer aligns to theprogram image, for example if the football player is no longer shown onthe display. The sketch annotations made in accordance with disclosedembodiments may be chronologically ordered and a chronological“position” of a sketch annotation within a program may indicate, with adegree of precision that is implementation specific, a portion of theprogram that was being watched when the sketch annotation was created.For example, a timestamp may be applied to or associated with a sketchannotation or an indication of the sketch annotation.

The above disclosed subject matter is to be considered illustrative, andnot restrictive, and the appended claims are intended to cover all suchmodifications, enhancements, and other embodiments which fall within thetrue spirit and scope of the present disclosure. Thus, to the maximumextent allowed by law, the scope of the claimed subject matter is to bedetermined by the broadest permissible interpretation of the followingclaims and their equivalents, and shall not be restricted or limited bythe foregoing detailed description.

What is claimed is:
 1. A content annotation method, comprising:receiving, from a first client associated with a first viewer viewingmultimedia content selected from television content, pay-per-viewcontent, and video on demand content, a first user input indicative of afirst annotation including an image and a second user input indicativeof a first annotation duration wherein annotations of the first viewerinclude source identification features indicative of the first viewer asa source of the annotations; wherein the source identification featuresare selected from: a source identification avatar and a sourceidentification icon; associating the first annotation with a firsttemporal location of the multimedia content; providing, by a dataprocessing system, the multimedia content, the first annotation, and thefirst temporal location to a second client associated with a secondviewer of the multimedia content, wherein, upon displaying themultimedia content, the second client displays the first annotation atthe first temporal location, for the first annotation duration,overlaying the multimedia content; and responsive to receiving a secondannotation, a second temporal location, and a second annotation durationfrom the second viewer, the first client, upon displaying the multimediacontent, displays the second annotation at the second temporal location,for the second annotation duration, overlaying the multimedia content.2. The method of claim 1, wherein: associating the first annotation withthe first temporal location includes storing chronological informationindicative of the first temporal location within the multimedia content.3. The method of claim 1, wherein the first annotation comprises animage of the multimedia content displaying at the time the first viewerasserted an annotation button or otherwise created the first annotation.4. The method of claim 1, wherein: the second client navigates to asegment of the multimedia content containing the sketch annotationresponsive to detecting an indication of the sketch annotation.
 5. Themethod of claim 1, wherein the user input comprises user assertion of anannotation button on a remote control device while the program ispresented to the first user.
 6. The method of claim 1, wherein the firstannotation is color coded to further distinguish it from furtherannotations from sources.
 7. The method of claim 1, wherein the firstuser input comprises user input to a cellular telephone communicativelycoupled to the first client, wherein the first client is a set top box.8. The method of claim 7, wherein the cellular telephone receives thefirst user input via a touch screen of the cellular telephone.
 9. Themethod of claim 7, wherein the cellular telephone is enabled to receivethe first user input via a stylus.
 10. The method of claim 3, whereinelements of the first annotation align to elements of a current image ofthe multimedia content.
 11. The method of claim 10, further comprising:removing the first annotation when the first annotation no longer alignsto the image.
 12. The method of claim 11, wherein: removing the firstannotation occurs in response to a change of scene in the multimediacontent.
 13. The method of claim 7, wherein the first annotation dataincludes textual information to further distinguish annotations of othersources.
 14. The method of claim 10, wherein the first annotationemphasizes a visible element of the multimedia content.
 15. A dataprocessing system suitable for use in a multimedia content deliverynetwork, the system comprising: a processor; a computer readable storagemedium including program instructions which, when executed by aprocessor, cause the processor to perform operations for annotatingmultimedia content, the operations comprising: generating an annotation,including an image, based on viewer input wherein annotations of a firstviewer include source identification features indicative of the firstviewer as a source of the annotations, wherein the annotation featuresare selected from: a source identification avatar and a sourceidentification icon; associating the annotation with: a temporallocation of the multimedia content; and a duration setting indicating anannotation duration; storing data indicative of the annotation, thetemporal location, and the annotation duration responsive to detectingan annotation request from a first client associated with a first viewerviewing the multimedia content, wherein the annotation is indicative ofa path of motion of a hardware element affected by body movement of thefirst viewer; recognizing a second viewer as a member of a collaborationgroup; and providing the annotation and the temporal location to asecond client associated with the second viewer in conjunction with thesecond viewer receiving the content wherein the second viewer views theannotation overlaying the multimedia content, for the annotationduration, during presentation of the multimedia content by the secondclient associated with the second viewer.
 16. The system of claim 15,wherein the temporal location includes chronological informationindicative of a chronological location within the multimedia content ofthe annotation.
 17. The system of claim 15, wherein the annotation iscolor coded to further distinguish it from annotations from othersources.
 18. The system of claim 16, wherein the first viewer input isprovided to a mobile communication device.
 19. The system of claim 18,wherein generating the annotation includes receiving viewer input from atouch screen coupled to the mobile communication device.
 20. The systemof claim 18, wherein the mobile communication device is a smart phone.21. A content annotation method, comprising: responsive to detectingviewer input indicating an annotation duration and including annotationinput representing of an annotation, including an image, from a firstviewer, the first viewer belonging to an annotation group, storingannotation data indicative of the annotation, wherein the annotationdata is associated with a chronological location of multimedia contentprovided to the first viewer, wherein the multimedia content is selectedfrom: television content, pay-per-view content, and video on demandcontent; wherein annotations of the first viewer include sourceidentification features indicative of the first viewer as a source ofthe annotations, wherein the annotation features are selected from: asource identification avatar and a source identification icon; andresponsive to a second viewer of the annotation group requesting themultimedia content, providing the annotation data and the multimediacontent to the second viewer wherein, upon presentation to the secondviewer, the annotation is displayed, overlaying the multimedia content,for a duration determined by the annotation duration.
 22. The method ofclaim 21, wherein the annotation image is indicative of a frame of themultimedia content displayed when the first viewer annotated themultimedia content.
 23. The method of claim 21, wherein the annotationincludes chronological information indicative of a chronologicallocation within the multimedia content of the annotation.
 24. The methodof claim 21, further comprising: generating an annotation requestresponsive to the first viewer asserting an annotation button on aremote control device.
 25. The method of claim 21, wherein theannotation is coded to further distinguish from annotations from othersources.
 26. The method of claim 25, wherein the annotation includestextual annotations to further distinguish the annotation fromannotations from other sources.
 27. A collaborative sketch annotationmethod, comprising: providing, by a first client, annotations, whereineach annotation includes a sketch image associated with a correspondingchronological position of a television program; storing, by the firstclient, annotation data indicative of: the annotations and thecorresponding chronological positions; and an annotation duration; andsending the annotation data to a second client, wherein the secondclient, responsive to receiving the annotation data, asynchronouslyaccesses the stored annotation data and displays the annotationsoverlaying the multimedia content for the annotation duration whilereceiving the television program; wherein annotations of the firstclient include source identification features indicative of the firstclient as a source of the annotations, wherein the annotation featuresare selected from: a source identification avatar and a sourceidentification icon.
 28. The method of claim 27, further comprisingdefining a plurality of users wherein the plurality of users includesthe second client.
 29. The method of claim 28, wherein the second clientnavigates the program by the annotations.
 30. The method of claim 29,further comprising identifying a selected recipient as the secondclient.